Note to self, rename #2258 after this is merged (there will be lots of conflicts).

This doesn't deprecate nicely. We should make dangerouslySetInnerHTML work for a release.

@zpao Will add.

Yea I guess this is helpful because you get the error message an it is easy.

If this wasn't easy we could just require a codemod since it's such a unique name.

On Sep 30, 2014, at 3:13 PM, Andreas Svensson [email protected] wrote:

@zpao Will add.

—
Reply to this email directly or view it on GitHub.

@zpao I've re-added dangerouslySetInnerHTML with a depreciation warning.

Why don't we have a utility helper for emitting warnings once per component and (optionally) with the component name automatically prefixed? ... Should I put up a PR for something like it?

Ugh. We should've done this earlier. If we do it now, it's not worth the headache. Maybe if we intro innerHTML?